Mobile data triangulation system and method for indexing, accessing and routing network resources

ABSTRACT

A computer-implemented method of managing computer network resources by one or more processors is provided. The method includes acquiring data from an external device over a network, storing operational programs and data in a storage, and compiling the acquired data into a live object. The method also includes linking resources identified in the live object via service modules and interfaces, activating the links of the identified resources to acquire information from the resources and to personalize performance of the resources, and creating a vectoring engine to implement specific objectives of the live object and an active plate. The method further includes creating a box that establishes an independent relationship with the live object, managing the service modules and interfaces of the system to execute the specific objectives, managing the box to query data contained in the live object, and transmitting results of the executed specific objectives to the external device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/204,177 filed Mar. 11, 2014, which claims the benefit of priority toU.S. Provisional Application No. 61/777,416, filed Mar. 12, 2013. Theentire disclosures of the above-identified applications, including thespecifications, drawings and claims are incorporated herein by referencein their entirety.

BACKGROUND

Field of the Disclosure

The present disclosure generally relates to a software-based computernetwork-resource management platform that uses mobile phones and othernetwork devices to capture and transmit event-defining data for instantconversion into an instrument by which to pursue the actionable oracquirable element of the event.

Background Information

As a platform, the tandem of smartphones and mobile apps provide asolution to many of the situations people encounter during the day. Butlimited by their structure and functionality, there is a far greaternumber of things for which they cannot provide a solution. With anever-growing number of people looking to their mobile devices forsolutions to the demands of day, the limitations of mobile appsrepresents a problem. Moreover, it's unlikely that the app paradigm canbe expanded to solve the problem—requiring the emergence of a new mobileplatform that is situationally-aware and proactive in its support forongoing user designated endeavors.

Evermore, people's ambitions and actions are echoed by network activity.Except as a link to resources, the networks themselves are not proactivein their support of these endeavors. They don't determine the mostefficient course of action nor do they proactively orchestrate thetimely availability of resources in its support or alteration.

SUMMARY OF THE DISCLOSURE

The present disclosure, through one or more of its various aspects,embodiments, and/or specific features or sub-components, providesvarious systems, servers, methods, media, and programs for interfacingcompiled codes, such as, for example, JavaScript scripts.

The disclosure relates to a software-based computer network-resourcemanagement platform that uses mobile phones and other network devices tocapture and transmit an event for instant conversion into an instrumentby which to pursue the actionable or acquirable element of the event.The vectoring engine-generating platform has sixteen major components:(A) Capture and Transmit Framework; (B) Transmission Processing; (C)Object Generator; (D) Actualizer; (E) Resource Vectoring EngineFramework (F) Traffic Recorder; (G) User Virtualization Framework; (H)Engine Manager/Player Framework; (I) Listening Post Framework; (J) EventRegistration Framework; (K) Financial Framework; (L) Box Library; (M)Code Library; (N) Service Module Library; (O) Graphic User InterfaceLibrary; (P) Service Module Framework. In addition to these, theplatform relies on nine major elements: (1) Resource Vectoring Engine;(2) Service Modules; (3) Live Objects; (4) Primal Objects; (5) Stamps,Codes & Indexes; (6) Plates; (7) Lockets; (8) Boxes; (9) Interfaces.Altogether, the components and elements are designed to synchronize theperformance and delivery of network accessible resources throughout thepursuit of the actionable or acquirable element of an originating event.

The resource management system will create a platform that will offer anew way of setting and executing a course of action. It will enable theemergence of new ways of supporting people's endeavors; enabling itsnetworks to proactively support the continuation of an activity or theresponses to an event, from their beginnings.

In one embodiment, there is a system for managing computer networkresources, including a transmission element to process data acquiredfrom an external source; an object generator to compile the dataacquired from the transmission element into a live object; an actualizerto link the resources identified in the live object via service modulesand interfaces; and a vectoring engine to implement the objectives ofthe live object and an active plate and manage the service modules andinterfaces of the system to execute the objectives.

In another embodiment, there is a computer-implemented method ofmanaging computer network resources, including at least one processorincluding processing data acquired from an external source; compilingthe data acquired from the external source into a live object; linkingthe resources identified in the live object via service modules andinterfaces; and implementing the objectives of the live object and anactive plate and managing the service modules and interfaces of thesystem to execute the objectives.

In still another embodiment, there is a computer readable storage devicethat stores a set of instructions for managing computer networkresources, the instructions when executed causing a computer to performoperations including processing data acquired from an external source;compiling the data acquired from the external source into a live object;linking the resources identified in the live object via service modulesand interfaces; and implementing objectives of the live object and anactive plate and managing the service modules and interfaces of thesystem to execute the objectives.

In one aspect, wherein the transmission element validates the dataacquired from the external source; extracts at least a portion of thedata and inserts identifiers system codes and indexes; and aggregatesthe at least a portion of the data, the system codes and the indexes andforwards the aggregated information to the object generator.

In another aspect, the object generator assembles the aggregated dataacquired from the transmission element by: scanning the aggregated datafor embedded algorithms, inserting additional identifiers, system codesand indexes received from at least one of user and event registrationdata, and formatting the aggregated data based on the embeddedalgorithms; codes the aggregated data by inserting header codes andindexes received from library sources; and creates the live object andthe active plate from the aggregated data.

In yet another aspect, the actualizer provides an instance of avectoring engine by using data in the live object to provide support ina continuously evolving manner; activates the link acquire informationfrom the resources and to personalize performance of the resources, andinterfaces with internal and external resources.

In still another aspect, the vectoring engine implements the objectivesusing: the active and a reserved plate defining instructions andresource designations corresponding to a stage of implementation; userdata providing a user data profile to personalize performance of thesystem; user resources designating the resources enabled on a user orsystem device; a communications manager interlacing active systemcomponents; and a controller extracting and posting the codes includedin the live object for use by the active system components, wherein thevectoring engine executes the instructions and resource designationsincluded in the live object and the active plate.

In another aspect, the live object and the active plate includeupdatable code-based instructions that govern performance of an instanceof the vectoring engine.

In yet another aspect, the instance of the vectoring engine coordinatesperformance of available system resources in furtherance of theobjectives.

In still another aspect, the service modules are dynamically managed inan evolving manner.

In yet one other aspect, the external source is at least one of a mobileand a network device, including plug-ins, to capture and transmitmarkers the system uses to initiate management of system resources.

In yet another aspect, the external source is a listening post tofacilitate the capture, transmission and integration of externalperformance altering data into the live objects, and communicate withthe actualizer.

In an aspect, the user data profile includes at least at least one ofthe user's language, mobile number(s), time zone, device ID's, usehistory, calendar, personal codes, personal networks, active boxes,active interfaces, vectoring engines, and onboard service modules.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is further described in the detailed descriptionwhich follows, in reference to the noted plurality of drawings, by wayof non-limiting examples of preferred embodiments of the presentdisclosure, in which like characters represent like elements throughoutthe several views of the drawings.

FIG. 1 is an exemplary system for use in accordance with one embodimentof the disclosure.

FIG. 2 discloses an exemplary capture and transmit framework inaccordance with one embodiment of the disclosure.

FIG. 3 discloses an exemplary transmission element in accordance withone embodiment of the disclosure.

FIG. 4 discloses an exemplary object generator in accordance with oneembodiment of the disclosure.

FIG. 5 discloses an exemplary actualizer in accordance with oneembodiment of the disclosure.

FIG. 6 discloses an exemplary vectoring engine framework in accordancewith one embodiment of the disclosure.

FIG. 7 discloses an exemplary traffic recorder in accordance with oneembodiment of the disclosure.

FIG. 8 discloses an exemplary user virtualization framework inaccordance with one embodiment of the disclosure.

FIG. 9 discloses an exemplary engine manager/player framework inaccordance with one embodiment of the disclosure.

FIG. 10 discloses an exemplary listening post framework in accordancewith one embodiment of the disclosure.

FIG. 11 discloses an exemplary event registration framework inaccordance with one embodiment of the disclosure.

FIG. 12 discloses an exemplary financial framework in accordance withone embodiment of the disclosure.

FIG. 13 discloses an exemplary box library in accordance with oneembodiment of the disclosure.

FIG. 14 discloses an exemplary code library in accordance with oneembodiment of the disclosure.

FIG. 15 discloses an exemplary service module library in accordance withone embodiment of the disclosure.

FIG. 16 discloses an exemplary graphic user interface library inaccordance with one embodiment of the disclosure.

FIG. 17 discloses an exemplary service module framework in accordancewith one embodiment of the disclosure.

FIG. 18 discloses an exemplary process diagram in accordance with oneembodiment of the disclosure.

FIG. 19 discloses an exemplary process diagram in accordance with oneembodiment of the disclosure.

FIG. 20 discloses an exemplary process flow of the system in accordancewith one embodiment of the disclosure.

DETAILED DESCRIPTION

The present disclosure, through one or more of its various aspects,embodiments and/or specific features or sub-components, is thus intendedto bring out one or more of the advantages as specifically noted below.

FIG. 1 is an exemplary system for use in accordance with the embodimentsdescribed herein. The system 100 is generally shown and may include acomputer system 102, which is generally indicated. The computer system102 may operate as a standalone device or may be connected to othersystems or peripheral devices. For example, the computer system 102 mayinclude, or be included within, any one or more computers, servers,systems, communication networks or cloud environment.

The computer system 102 may operate in the capacity of a server in anetwork environment, or the in the capacity of a client user computer inthe network environment. The computer system 102, or portions thereof,may be implemented as, or incorporated into, various devices, such as apersonal computer, a tablet computer, a set-top box, a personal digitalassistant, a mobile device, a palmtop computer, a laptop computer, adesktop computer, a communications device, a wireless telephone, apersonal trusted device, a web appliance, or any other machine capableof executing a set of instructions (sequential or otherwise) thatspecify actions to be taken by that device. Further, while a singlecomputer system 102 is illustrated, addition embodiments may include anycollection of systems or sub-systems that individually or jointlyexecute instructions or perform functions.

As illustrated in FIG. 1, the computer system 102 may include at leastone processor 104, such as, for example, a central processing unit, agraphics processing unit, or both. The computer system 102 may alsoinclude a computer memory 106. The computer memory 106 may include astatic memory, a dynamic memory, or both. The computer memory 106 mayadditionally or alternatively include a hard disk, random access memory,a cache, or any combination thereof. Of course, those skilled in the artappreciate that the computer memory 106 may comprise any combination ofknown memories or a single storage.

As shown in FIG. 1, the computer system 102 may include a computerdisplay 108, such as a liquid crystal display, an organic light emittingdiode, a flat panel display, a solid state display, a cathode ray tube,a plasma display, or any other known display.

The computer system 102 may include at least one computer input device110, such as a keyboard, a remote control device having a wirelesskeypad, a microphone coupled to a speech recognition engine, a camerasuch as a video camera or still camera, a cursor control device, or anycombination thereof. Those skilled in the art appreciate that variousembodiments of the computer system 102 may include multiple inputdevices 110. Moreover, those skilled in the art further appreciate thatthe above-listed, exemplary input devices 110 are not meant to beexhaustive and that the computer system 102 may include any additional,or alternative, input devices 110.

The computer system 102 may also include a medium reader 112 and anetwork interface 114. Furthermore, the computer system 102 may includeany additional devices, components, parts, peripherals, hardware,software or any combination thereof which are commonly known andunderstood as being included with or within a computer system, such as,but not limited to, an output device 116. The output device 116 may be,but is not limited to, a speaker, an audio out, a video out, a remotecontrol output, or any combination thereof.

Each of the components of the computer system 102 may be interconnectedand communicate via a bus 118. As shown in FIG. 1, the components mayeach be interconnected and communicate via an internal bus. However,those skilled in the art appreciate that any of the components may alsobe connected via an expansion bus. Moreover, the bus 118 may enablecommunication via any standard or other specification commonly knownand, understood such as, but not limited to, peripheral componentinterconnect, peripheral component interconnect express, paralleladvanced technology attachment, serial advanced technology attachment,etc.

The computer system 102 may be in communication with one or moreadditional computer devices 120 via a network 122. The network 122 maybe, but is not limited to, a local area network, a wide area network,the Internet, a telephony network, or any other network commonly knownand understood in the art. The network 122 is shown in FIG. 1 as awireless network. However, those skilled in the art appreciate that thenetwork 122 may also be a wired network.

The additional computer device 120 is shown in FIG. 1 as a personalcomputer. However, those skilled in the art appreciate that, inalternative embodiments of the present application, the device 120 maybe a laptop computer, a tablet PC, a personal digital assistant, amobile device, a palmtop computer, a desktop computer, a communicationsdevice, a wireless telephone, a personal trusted device, a webappliance, a television with one or more processors embedded thereinand/or coupled thereto, or any other device that is capable of executinga set of instructions, sequential or otherwise, that specify actions tobe taken by that device. Of course, those skilled in the art appreciatethat the above-listed devices are merely exemplary devices and that thedevice 120 may be any additional device or apparatus commonly known andunderstood in the art without departing from the scope of the presentapplication. Furthermore, those skilled in the art similarly understandthat the device may be any combination of devices and apparatuses.

Of course, those skilled in the art appreciate that the above-listedcomponents of the computer system 102 are merely meant to be exemplaryand are not intended to be exhaustive and/or inclusive. Furthermore, theexamples of the components listed above are also meant to be exemplaryand similarly are not meant to be exhaustive and/or inclusive.

Described in detail below is a network-accessible, resource managementsystem that manages the timely availability of information,communication, and algorithmic resources relevant to a user's activity.Such activities are deemed to have a starting point that can be detectedby the system using an initial signaling transmission. As explainedbelow, the system also uses subsequent signaling transmissions as ameans to modify the performance of the controlling agents it creates.

Upon receipt of the transmission, which includes a set of identifies andcodes that identify the user and the respective event, the data isextracted and combined with data already residing in the system as thebasis for the creation of a unique instance of a controlling agent,referred to herein as a resource vectoring engine, that will manage theongoing, timely availability of the resources necessary to accomplishthe endeavor. The system is self-contained in that it not only vectoringengines, but also provides the local (cloud-based) and remote (userdevice-based) software environment they run in.

With reference to the following components and elements, an instance ofa vectoring engine is created having a performance that echoes theintent of its originating transmission, as described below. For example,if the user was interested in purchasing a used car that was for sale byits owner (and its owner has completed the registration process) thevectoring engine created for that event would provide resources fittingto the user's pursuit and acquisition of the subject vehicle.

FIG. 2 discloses an exemplary capture and transmit framework inaccordance with one embodiment of the disclosure. The capture andtransmit framework (component A) may be a software application thatresides on the mobile devices or on the desktop devices (or any otherdevice connected to the system) of the system's users. The softwareenables the transmission of the identifiers and codes the system usersto identify the user and the respective “registered event” (see,component J). In its performance, the framework works in concert withsystem-compliant plug-ins. Individual plug-ins are respective to eachmode of ingest; such as the entry of numbers, the scanning of a barcode,voice activation, GPS, etc. Upon receipt, and with the aid of theframework, they convert the mode of ingest into a format that issystem-compliant. It is noted that plug-ins work in concert with amatching component B plug-in, Component A also includes thetransmittable instruction codes that instruct the system to do suchthings as make it possible for user to “clone” and share a vectoringengine with another user. Further, the framework can support plug-insthat facilitates the attachment of notes and photographs. Additionally,the component can accept and display messages and interfacescommunicated to it by component B (transmission processing) in responseto a respective transmission. Moreover, the capture and transmitframework may also support the capture and transmission of theidentifier by a third-party proxy.

FIG. 3 discloses an exemplary transmission element in accordance withone embodiment of the disclosure. The transmission element (component B)may be a an application, such as a local software application, thatsupports plug-ins. Together with the plug-ins component B receives,validates, formats, and incorporates data from other supportingcomponents into the information received from component A. Component Bis supported by the event registration component, the uservirtualization framework component, and the graphic user interfacelibrary component, each of which is described in more detail below. Inconcert with these, component B carries out a number of processes tovalidate the transmission, extract data and coded instructions, insertsstamps, system codes and locators. Upon completion, the data, codes,locators, etc. are assembled, bundled or aggregated and forwarded to theobject generator (component C). It is appreciated that although thedata, etc. is described as assembled, bundled or aggregated, it is notlimited to the described embodiment. Any method of transmitting the datamay be used as readily understood in the art.

FIG. 4 discloses an exemplary object generator in accordance with oneembodiment of the disclosure. The object generator (component C) may bean application, such as a local software application. Having three (3)phases, the components first phase (assemble) acquires the dataaggregated by component B (transmission processing), scans its makeup,then based on the determinations of embedded algorithms, insertsadditional codes/locators/identifiers it pulls from components G & J(user virtualization & event registration) then formats and transfers tothe next stage (codify). Based on the determinations of embeddedalgorithms, the codify phase inserts header codes & locators found incomponents L, M and O (box library, code library, and graphic interfacelibrary). Upon completion, the aggregate is transferred to the thirdphase (strike). The algorithms of this phase evaluate the makeup of the“aggregate” and strikes (creates) one or more live objects. Thedetermination of the number is based on instruction found in theoriginating transmission or in the user virtualization component or theevent registration component. These instructions include the locatorsnecessary to route them to their respective users or devices. Further,respective objects may have variations in the makeup of its data. Uponcompleting the striking process, the live object(s) is forwarded tocomponent D (actualizer).

FIG. 5 discloses an exemplary actualizer in accordance with oneembodiment of the disclosure. The actualizer (component D) may be anapplication, such as a local software application, that uses the datafound at a respective live object to “actualize” a unique instance of avectoring engine framework. In this context, the term “actualize” meansto provide support for a continuously evolving state. Its initial act isto activate links to the resources identified in the live object. Thisincludes the transfer of the information necessary to personalize theperformance of the resources. The second act is to activate the link tothe user virtualization component (component G). The third act is toserve as a bus-like interface between an instance of a vectoring engineand the components denoted below. To function in this capacity, theactualizer manages the flow of information between an instance of avectoring engine and other components and elements, specifically theevent registration framework component, the listening post frameworkcomponent, the user virtualization framework component, and the trafficreporter component, all described in more detail below. It isappreciated, however, that the actualizer is not limited to the stepsnoted above, and may include more or less steps as required.

FIG. 6 discloses an exemplary vectoring engine framework in accordancewith one embodiment of the disclosure. The resource vectoring engineframework (component E) may be a software application, such as a hybrid(remote and local) software application that, together with theactualizer, creates a unique instance of a vectoring engine, whichimplements the objectives of the live object embedded therein and thoseof the current (active) plate. The resource vectoring engine may be, forexample, a hybrid (remote and local) instanced software application thatuses an embedded live object, the user's virtualization frameworkmodules and backer supplied plates to dynamically manage the system'sservice modules to execute toward the desired goal. This component issupported by the actualizer component, the graphic user interfacelibrary component and backer app interfaces. These components includeresources necessary to the performance of a vectoring engine and can beaccessed both directly and indirectly by the vectoring engine asdictated by its state predefined progress. Boxes having dotted linesdenote an off-board resource, component or element that both supportsand is supported by a vectoring Engine. Active plate and reserve platesinclude the “backer” defined instructions and resource designationsfitting to a particular stage of support the vectoring engine isproviding. The active plate is the plate that is in current use, andreserve plates are not in active use. An instance of a plate exists bothin the registration component and in the vectoring engine. User data is,for example, data extracted from the user data abstract included in theuser virtualization component and designated (within a plate or a liveobject as necessary to the performance of the vectoring engine—forinstance the language of the user. User resources denote a listing ofplug-ins, media players, interfaces, boxes and other system resourcesthat have been enabled on a device or in the user virtualizationcomponent. The communications manager acts as a bus-like interfacebetween active (non-dotted line) components in the figure, whereas thecontroller component extracts and posts the codes included in a liveobject for use by the dependent components. It also receives progressreport codes from these dependent components and writes them to the liveobject. A live object includes the updatable code-based instructionsthat along with the active plate govern the performance of an instanceof a vectoring engine. A vectoring engine process flow can be instructedto operate in one of two modes—automatic initiation mode or manualinitiation mode. Upon initiation, the controller sets about to executethe instructions included in the active plate and in reliance of thedesignated suite of resources.

FIG. 7 discloses an exemplary traffic recorder in accordance with oneembodiment of the disclosure. The traffic recorder(component F) may be asoftware application, for example a local software application, thatrecords and reports the instancing of vectoring engines and usage ofeach engine; merging the usage into a single report. The merging of datainto a single report can be done using any technique understood to theskilled artisan. Moreover, the report is not limited to a single report,but may include one or more reports. Optionally, the report will be madeavailable to the financial framework component, described below. Thetraffic recorder component is supported by the actualizer component andoptionally by the financial framework component. The option may beinvoked, for example, in conjunction with deployment of the system wherea desire for monetization component exists.

FIG. 8 discloses an exemplary user virtualization framework inaccordance with one embodiment of the disclosure. The uservirtualization framework (component G) may be a software application,such as a local software application, that includes components thatsupport various user-centric interests. The user registration anddownload support component supports the new user registration process,which includes downloading the capture and transmit framework softwareand the engine manager/player framework software. The enginemanager/player communications component manages communication betweenthe user virtualization framework and the related user graphicframework. The service module library component includes a list of andlinks to onboard (remote/user downloaded) service modules. The user dataabstract component includes the data profile the system uses topersonalize the performance of the system and is without restriction asto type. Typical of its contents are the user's language, mobilenumber(s), time zone, device ID's, use history, calendar, personalcodes, personal networks, active boxes, active interfaces, vectoringengines, onboard service modules, etc. Drawing from and adding to thisdata, are the following components: capture and transmit framework,transmission processing, object generator, actualizer, resourcevectoring engine framework, event registration framework, enginemanager/player framework, box library; code library, service modulelibrary, and the graphic user interface library.

FIG. 9 is an exemplary engine manager/player framework in accordancewith one embodiment of the disclosure. The engine manager/playerframework (component H) may be a software application, such as a remote,plug-in supporting, software application, that provides the collectivemanagement of, and the interfaces to, the user's collection of vectoringengines, boxes and onboard service modules. The composition andstructure of component 11 varies to match the interfacing needs of theuser's vectoring engines, boxes, onboard service modules, calendar, theuser abstract, and other items that may come to be added by the user.The manager/player framework (component H) interacts with the uservirtualization framework component, the graphic user interface library,and the user's vectoring engines. Interactions with other componentsvary based on the composition of the engine manager/player component. Inthe case of manual activation of a vectoring engine, manual activationsignaling is a function of the engine manager/player framework. Theactivation process triggers changes within the component and componentG, which notifies the actualizer (component D) and in turn notifies thevectoring engine and attendant service modules of the state ofreadiness.

FIG. 10 is an exemplary listening post framework in accordance with oneembodiment of the disclosure. The listening post framework (component I)may be software application, for example a hybrid (remote and local),plug-in supporting, application, that facilitates the capture,transmission, and integration of external performance altering data intothe live objects. Often during the lifecycle of a personal endeavor,external factors emerge to have a bearing on the endeavor. Thiscomponent provides the means to reconcile the performance of a vectoringengine with these factors. To do so, the Listening Post Frameworkoperates in a manner similar to merger of the capture & transmitframework and the transmission processing framework. Distinguishingitself from these is the ability to communicate directly to therespective live object through the actualizer—having already beensignaled by the actualizer of the instancing and activation of arespective vectoring engine.

FIG. 11 is an exemplary event registration framework in accordance withone embodiment of the disclosure. The event registration framework(component J) may be a software application, for example a hybrid(remote and local), plug-in supporting, application, that provides a“backer,” with the ability to have an event echoed by personalizedinstances of a vectoring engine. A “backer” is, for example, anindividual who has engaged in the event registration process that is aprerequisite for the instancing of a vectoring engine that echoes theevent that it's linked thereto. The framework enables the backer tospecify the engine's performance and monitor and interact with eachengine's user. The event registration framework captures and providesrelevant data directly or indirectly to: the capture and transmitframework, transmission processing, object generator, actualizer,financial framework, box library, code library, graphic user interfacelibrary, and the service module library.

The event registration framework component includes, but is not limited,to registration processes, resource designations, locket creation, andplate creation. Similar to a keyframe used in graphics animation, platesinclude the “backer” defined instructions and resource designationsfitting to a particular stage of support the vectoring engine isproviding. During the respective stage, the plate defines theperformance parameters of its associated vectoring engine. During thecourse of operation, it generates progress indicators that signal thevectoring engine when to activate a new or prior plate. Further a“backer” can modify a plate or create new plates at any time usingsoftware provided during the registration process. A Locket may be, forexample, a local software container that that holds in one place theinformation generated during the registration process, including thebacker authored plates. A primal object may be, for example, a softwareobject that services as a generic representation of the actionable oracquirable element a vectoring engine is programmed to support. A primalobject is used by “Box” to preface a related query.

FIG. 12 is an exemplary financial framework in accordance with oneembodiment of the disclosure. The financial framework (component K) maybe a software application, such as a local software application. Thecomponent is invoked in conjunction with deployments of the system wherethe need for a monetization component exists. In such case, thecomponent receives information from the event registration component andfrom the traffic recorder component regarding and vectoring engineinstancing and service module usage. These reports are used as the basisfor billing a vectoring engine's backer and distributing the proceeds tothe respective designated parties.

FIG. 13 is an exemplary box library in accordance with an embodiment ofthe disclosure. The box library (component L) may be a softwareapplication, for example a local software application that includes andmanages the system's boxes. A box may be, for example, a softwareapplication that is used to establish an independent relationship withthe live object included in an engine or multiple engines. The productof the relationship is defined by the box. Further, a box can alsoinclude other boxes: with each “superior” box defining its ownrelationship and output. The contents of the box library are accessibleand available to the event registration framework, object generator,user virtualization framework, and the engine manager/player framework.Further, its attendant codes are kept both internally and in the codelibrary component, described below.

FIG. 14 is an exemplary code library in accordance with one embodimentof the disclosure. The code library (component M) may be a softwareapplication, such as a local software application, that includes andmanages the system's stamps, codes & indexes. Stamps, codes and indexesare numerical entries that the vectoring engine uses to communicate backand forth with codependent components. The contents of the code libraryare accessible and available to the event registration framework, objectgenerator, user virtualization framework, and the engine manager/playerframework, the graphic user interface library, service module library,and the box library.

FIG. 15 is an exemplary service module library in accordance with oneembodiment of the disclosure. The service module library (component N)may be a software application, such as a local software application,that includes and manages the system's service modules, defined below.The contents of the service module library are accessible and availableto the following components: the event registration framework,transmission processing, object generator, and the engine manager/playerframework. Further, its attendant codes are kept both internally and inthe code library.

FIG. 16 is an exemplary graphic user interface library in accordancewith an embodiment of the disclosure. The graphic user interface library(component O) may be a software application, such as a local softwareapplication, that includes and manages the system's graphic userinterfaces. A graphic user interface may be, for example, the graphicuser interface used to interact with a vectoring engine or box. Anengine may elect to use any number of interfaces during the performanceof its duties. The contents of the Service Module Library are accessibleand available to the following components: the event registrationframework, transmission processing, object generator, uservirtualization framework, and the engine manager/player framework.Further, its attendant codes are kept both internally and in the codelibrary.

FIG. 17 is an exemplary service module framework in accordance with oneembodiment of the disclosure. The service module framework (component P)may be a software application, such as a local software application. Inits performance, the framework works in concert with system-compliantplug-in service modules. A service module is a software applicationdesigned to perform a single task, such as send a text message or createa network among the people represented by vectoring engines within the auser's collection. Within the designation there are three major classes:Receptor—which is used to receive and process incoming transmissions;Process—which works in conjunction with vectoring engines to manageexternal information and communication resources; and System—which areused throughout the system to support internal processes.

Regarding process service modules, the system is able to customize theirotherwise generic performance by way of the timely insertion of codes,locators, identifiers, and other forms of metadata by the vectoringengine's controller. The modules also communicate the results of theirefforts back to the controller so as to make it possible for thecontroller, in conjunction with instructions contained in the activeplate, to assess progress and potentially signal the activation of a newactive plate.

FIG. 18 illustrates an exemplary process diagram in accordance with oneembodiment of the disclosure. The diagram shows users, for examplePC/laptop, tablet, phone, along with part of the event registrationframework. The figure generally illustrates the procedures by which abacker of the system registers and sets-up. A “backer” is the individual(but not limited to an individual) who has engaged in the eventregistration process for the instancing of a vectoring engine. In orderto create one or more “lines” of engines, the financial “backer” of theline(s) downloads an application that manages the system's registrationprocess and consolidates the general management of the “backers” “lines”of engines. The term “line” is indicative of an event registration“Locket” from which similar vectoring engines are instanced. Separateregistrations result in separate “lines” of vectoring engines (step A).(See, Component J: Event Registration Framework.) In step B, the systemgenerates its resource vectoring engines (“Engine”) using informationobtained during the event registration process. (See, the EventRegistration Component: Component J.) The event registration process cantake place prior to the general engine generation process or concurrenttherewith. During the course of this process, a locket is created toinclude pointers to backer designated resources. Component N (servicemodule library) includes the software applications that serve both as aresource and processor of designated resources and Component O (graphicuser interface library). Component L (box library) includes the softwareapplications that serve as a resource to expand the usefulness of thesystem's Engines. The service modules, primal objects, plates, boxes,interfaces and component I (listening post framework). Each of thesecomponents and elements has a role in the event registration process,along with component K (financial framework), which manages (inconjunction with component F (traffic recorder)) the financial aspect ofthe registration, creation, and use of the system's engines. It isunderstood that the described embodiments are exemplary and not intendedto limit the scope of the disclosure. For example, the registrationprocess does not have to include each of the listed components andelements described above, but may include any variation of componentsand elements set forth in this disclosure. At the completion of thebacker registration process, the backer is supplied with a plug-in thatmanages interactions with a backer's new “line” of vectoring engines,including altering their performance. A backer can modify a plate orcreate new plates at any time using software plug-ins. In addition, thebacker is issued an identifier (a registration number, graphic, or otherelement) a user can capture and transmit using a capture andtransmission plug-in installed on his or her mobile device (step C). Thecapture and transmit framework may also support the capture andtransmission of the identifier by a third-party proxy.

FIG. 19 illustrates another exemplary process diagram in accordance withone embodiment of the disclosure. The figure generally illustrates theprocedures by which a user registers and sets-up with the system. Usersregister and set-up on the system and download software-based extensionsto component A (capture and transmit framework), and component H (enginemanager/player framework) and optional plug-ins. Users may also accessand/or download component G (user virtualization framework), whichincludes the user registration framework and download support.

FIG. 20 illustrates an exemplary process flow of the system inaccordance with one embodiment of the disclosure. In step 1: using hismobile device, PC or any other device connected to the system, and theappropriate capture and transmit plug-in (component A) (or by proxy), auser captures and transmits the identifier to component B (transmissionprocessing), which includes a respective receptor service module.Component B may also respond to the receipt of the transmission byreturning to the user an additional interface by which to refine thetransmission or for use in subsequent listening post related updates(see, component I: listening post framework.) If the identifier isincorrect, the transmission processing component will undertake anexchange with the user to rectify the incorrect entry.

In step 2: the system is designed to support a wide-range of identifiertransmission modes (component B), such as keypad, barcode, voice, text,facial recognition, and GPS. Each of these modes has a respectivereceptor services module with a corresponding component A plug-in. Uponreceipt of an identifier transmission, together with the respectivereceptor service module, the component undertakes a number of steps tovalidate the transmission, extract data and coded instructions, andinsert stamps, system codes and locators; some of which are retrievedfrom the event registration component and the user virtualizationframework component. Upon completion, the data, codes, and locators areaggregated and/or bundled (“bundle”) and forwarded to component C(object generator).

In step 3, upon receipt of a bundle from component B, component C(object generator) creates a live object using the contents of theaggregation and/or bundle and data from the event registrationcomponent, the user virtualization framework component, the code librarycomponent, the box library component, and the graphic user interfacecomponent. Upon completion of the live object, it is forwarded tocomponent D (actualizer).

In step 4, upon receipt of a live object from component C, component D(actualizer) uses coding contained in a live object to create a uniqueinstance of a vectoring engine framework (component E). In this context,the term “actualize” means, but is not limited to, providing support fora continuously evolving state. To function in this capacity, theactualizer component gains support from the event registration frameworkcomponent, the listening post framework component, the user frameworkcomponent, and the traffic reporter component. Upon completion of aunique instance of a vectoring engine framework (component E), componentD sends an access/activation link to the respective user virtualizationframework (component G), the listening post framework (component I) andthe traffic recorder (component F).

In step 5, upon receipt of the access/activation link, the uservirtualization framework component (component G) posts the link fordownload to component H (engine manager/player framework).

In step 6, upon the user's activation of the engine manager/playerframework (component H); component E (an instance of the vectoringengine) access/activation link is downloaded to the manager/player foractivation. The activation process effects changes within the componentand component G (user virtualization framework) and notices externalcomponents of its state of readiness. These include, for example, theactualizer and listening post components; which in turn notify theirrespective supporting service modules and components.

In step 7, upon activation, component H (the interface element) andcomponent G (the transactional element) work together to support the usea respective engine.

In step 8, during the course of its use, the performance of a vectoringengine is subject to modification from input from component H (enginemanager/player framework) user virtualization framework, component I(listening post framework), component J (event registration framework),the service modules, plates, boxes, and graphic user interfaces.

In optional step 9, using input from component F (traffic recorder) thefinancial framework supports billing, collection, and distribution offunds respective to the creation and user of a vectoring engine and useof a respective box.

The process flow described above creates and sustains asituationally-aware, proactive resource network to automate support forongoing personal, collaborative, intersecting and contiguous endeavorsin such fields as: education, buying & selling (retail and commercial),logistics, sports and entertainment, financial and commodity trades,social networking, medicine, emergency response, disaster relief,government and military operations, the maintenance of civil order, oiland natural gas production, environment and conservation, hospitality,advocacy, banking, and computer-modeled monetary systems.

Described herein below are non-limiting examples of the process flowidentified above. Imagine a user passing through a small out of the waytown and happen upon an intriguing restaurant. The food is fantastic,particularly the dessert. The wine is award winning and local. Certainthat the user will forget the experience, he creates a vectoring engine.The user is happy because he found something he likes and want to keepthe connection. The restaurant is equally happy because the engine willserve as a digital bond that's based on a good experience. When the userreturns home, he downloads the engine's interface onto his mobile deviceor computer and the bond will begin to grow. For example, first the usermay share it with friends. Next, he can access the link to the winery.Ordering a case of wine is simple because the engine knows which one youordered at the restaurant. Next, the user asks the engine to send a textmessage when the user's GPS detects that he is in the vicinity of therestaurant again. A few weeks later, the user is hosting a dinner party,with the restaurant somewhat forgotten, and decides to use the searchfeature that manages his engines for suggestions. It's then that theuser rediscovers the restaurant and remembers the dessert; so he usesthe engine to ask the chef for the recipe. There's no need to describeit; the engine knows. The next day the user receives a copy of therecipe; along with it is an invitation to a special seating, including adiscount coupon.

In the educational world, content may be created by the publishers andmaintained in digital media. Any content provider can enable its contentby creating a Locket for each textbook. Often important to both schooldistrict and content publisher alike, are dynamic, bi-directionalchannels. As a publisher updates and approves publishing of the contentin a given textbook, that content is automatically pushed to each andevery instance of a textbook's vectoring engine, thereby keeping thematerials fresh. Also, course materials and augmented services may beoffered in in a variety of delivery options, for example, developing,basic and advanced. This gives both student and teacher truedifferentiated learning across every course.

An example of such content, publication and vectoring engine for use inthe system is illustrated below. Over the summer, Ms. Brown, a fourthgrade teacher, attended conferences offered by a Third-Party EducationLicensee. Covered in that conference were the details about the system'splatform, how/when to use it, best practices, features, etc. Featureschosen by the school district provide a means for the studentscollaborate amongst themselves in a secure, monitored environment, but,in addition to her regular school hours, Ms. Brown would be availableonline Monday and Thursdays from 6 PM to 7 PM where she can interactwith students via an online video classroom. Students can ask questionsand see and hear Ms. Brown explain the answers to unit study issues.Students unable to make the live session, or wish to replay the sessionfor clarity, could watch the archived version sometime later as theyhave time.

At the beginning of the school year, the school district is signed up toprovide instances of Vectoring Engines to every teacher and student. Aspart of that process, teachers and students are assigned accounts.Within the first couple weeks of school, students are evaluated forproficiency in math. They are grouped into one of three categories, forexample: developing, basic and advanced. Through her client application,Ms. Brown imports her class roster and assigns each student to one ofthe three differentiated learning categories above matched to thestudent's account. While the basic and advanced students might excelwhen a particular teaching method is used, the students in thedeveloping group might benefit from alternate method(s) of instruction.Using her application, Ms. Brown can ensure that each student receivesinstruction based on content and teaching methods developed by thepublisher which are tailored to the abilities and needs of each group.Ms. Brown introduces the concepts of long division. She goes overexamples, and assigns homework from an enabled textbook (course ofinstruction). Instead of each student writing down the homework, Ms.Brown, for example in a drag-and-drop environment, assigns homework toeach child based on his or her level of proficiency in to the “backer”app interface.

At home, the children access the related Vectoring Engine and engagethat night's homework. The homework is developed by the contentpublisher and is based on the lesson Ms. Brown taught that day, so ananswer key is integrated with that section's vectoring engines activeplate. The homework is instantly graded and both the fact that a studentcompleted the homework and the resulting grade are automaticallyrecorded in Ms. Brown's online grade-book. Further, let's say a studentnamed Billy gets numbers four and seven wrong. Upon grading the work,the vectoring engine tells Billy he got two wrong, and presents him witha couple of videos and lessons which reteach the concepts he hadn'tcompletely mastered. If desired, he can watch the videos and do a fewmore problems, the results of which can be sent automatically to Ms.Brown.

For her part, as she prepares for the next day (either later that nightor early the next morning using the “backer” app interface), Ms. Browncan quickly and easily see which students did what, and, importantly,maximize her valuable time by quickly and easily seeing how each studentdid on the prior night's work. Within a few minutes she can prioritizeher for time the next day. Accordingly, the system is facilitating thedelivery of personalized and differentiated learning, ensuring that eachstudent is taught in a way that maximizes both dollars and time spent.This allows private, secure interaction between the student andinstructor, and allows private network platforms for interactions forteacher to teacher, principle to principle, and superintendent tosuperintendent with a goal for each to develop and share “bestpractices.”

Other examples include the utilization of expositions. World-wide thereare 10,000 expositions each year, plus countless seminars, workshops,conferences and symposiums. The system may be utilized in the expositionas follows. Assume in one example that there is a manufacturer ordistributor of golf clubs. The manufacturer or distributor attends a PGAmerchandise show, and brings 10 new drivers that are sold as part of theinventory. As do all exhibitors, a booth is set up, complete withmonitors for running looped videos highlighting my products, as well asproduct literature and samples. A couple of representatives man thebooth. The show starts and the booth garners a lot of traffic—far morethan the booth representatives can efficiently handle. While fosteringand developing relationships with every attendee who walks into thebooth would be preferred, it is beyond the capabilities of the fewpeople maiming the booth. However, as part of the registration processto be an exhibitor, the manufacturer/distributor signed up to have theproducts and content undergo the event registration process.

The registration process makes it possible to quickly and easilyorganize the content and information about the products in the booth forattendees into attendee-specific instances of vectoring engines. Now, ifrepresentatives are occupied with other attendees when attendee “Bill”walks into the booth, the system can handle it. Bill's interested in aspecific driver, and, in addition to that product's literature. Billsimply enters the booth number into a software plug-in on his or herphone, along with the driver and other items of interest that areregistered. The resulting instance of a vectoring engine is posted tothe user's virtualization component for download onto a user's device.Bill clicks on some of the content included in the vectoring enginesinterface: 3D views of the driver, videos about manufacturing and tourplayer testimonials, etc. Bill's interested, but the price is too steepfor him today. As Bill closes the interface, he is presented with aquestion: why didn't you buy the driver today? Radio buttons have beenincluded for him to explain his reason(s) why. One of those is “Cost toohigh”. As an immediate follow-up, the vectoring engine asks Bill if he'dbe buying it today if it meant a 10%/15% discount. If Bill clicks yes,for example, then the vectoring engine immediately takes him to theconfiguration interface, then from there to the order confirmation andshipping interface. Since the date the show ends is known, shipping isautomatically configured so it arrives on or before he gets home. IfBill answers no again, he can be prompted for the price point at whichhe'd be interested in buying. When Bill leaves the show he still has theVectoring Engine for that driver. That vectoring engine, via a servicemodule and user and “backer” interfaces can create a bi-directionalchannel between Bill and the manufacturer/distributor company. So, forexample, if the manufacturer/distributor has chosen to interface aproduct database with the vectoring engine, and at some point down theroad the price is dropped on the driver Bill wants at the price point heindicated, both Bill and a representatives could be alerted that Billcan get the driver at the price he wants. Through the same vectoringengine, Bill can proceed with the configuration and order confirmationand shipping.

The system described above offers numerous advantages, including work ashidden layers, parent/child dependencies, and other permutations Otheradvantages include exacting, personalized match of resources to thesituation at hand; ongoing matching of resources to current needs(performance shifting); instant onsite availability: cloning to all of auser's devices; instantly sharable with other parties; sellsynchronization on the user's and other parties devices; operation inconjunction with a transactional revenue component; work in unison withother vector engines.

The vectoring engines of the disclosure may be differentiated frommobile Apps in the following non-limiting ways:

-   -   A. Apart from a phone's operating system mobile apps do not run        inside a comprehensive environment. Vectoring engines run inside        a comprehensive operating environment.    -   B. Mobile apps do not operate in the capacity of an engine using        a live (read/write) object and surrounding controller to        orchestrate the timely application of specialized (algorithmic)        services modules; with the live object supplying the        instructions governing their performance. Vectoring engines, on        the other hand, do operate in the capacity of an engine, using a        live (read/write) object and surrounding controller to        orchestrate the timely application of specialized (algorithmic)        services modules: with the object supplying the instructions        governing their performance.    -   C. The coded instructions governing the performance of mobile        apps are not a derivative of datasets supplied by the parties to        an activity. The coded instructions governing the performance of        vectoring engines are a derivative of datasets supplied by the        parties to an activity.    -   D. Mobile apps are not designed to support an activity        representing the progressive execution of a complex scenario        having the potential for variations from the standard model        script. Vectoring engines are designed to support an activity        representing the progressive execution of a complex scenario        having the potential for variations from the standard model        script.    -   E. Mobile apps provide their own graphic user interfaces.        Vectoring engines typically do not, but rather support        interactions via library-based graphic user interfaces.    -   F. A user's mobile apps do not communicate with each other.        Vectoring engines have the ability to communicate with each        other, including each other's performance. Vectoring engines        also have the ability to communicate with compliant mobile apps.    -   G. Mobile apps are not created on-demand to support a        user-specific personal activity. Vectoring engines are created        on-demand to support a user-specific personal activity.    -   H. Mobile apps are not designed to support a user-specific        personal activity from onset through to its completion.    -   I. Mobile apps cannot be created on-demand to capture an event        or happening that the user is in the midst of or passing by;        including its participants. Vectoring engines can be created        on-demand to capture an event or happening a user is in the        midst of or passing by; including its participants.    -   J. Mobile apps cannot alter their performance in response to        variations in the user's approach to the activity. Vectoring        engines can and do alter their performance based on variations        in the user's activities.    -   K. Mobile apps cannot alter their performance, in regard to a        user-specific activity based on external signaling        transmissions. Vectoring engines can and do alter their        performance based on external signaling transmissions.    -   L. The performance of mobile apps is not influenced by a        comprehensive profile of its user; including outcome or current        state of other activities. The performance of a vectoring engine        is influenced by a comprehensive profile of its user; including        the outcome or current state of other activities.    -   M. Mobile apps do not spontaneously, or otherwise, spawn another        mobile app.

Vectoring engines can spawn another vectoring engines having differentfunctionality.

-   -   N. Mobile apps cannot be cloned and sent to another user or        users. Vector engines can be cloned and sent to another user or        users.    -   O. Mobile apps cannot be cloned and sent to other users to        create nodes on a neural network. Vectoring engines can be        cloned and sent to others (including devices and machines) to        establish a neural network.    -   P. Mobile apps are not capable of defining and managing the        responsibilities and resources available to the parties        (including machines) that are represented as nodes on a neural        network.    -   Q. Mobile apps are not capable of defining and managing the        responsibilities and resources available to the parties        (including machines) that are represented as nodes on a neural        network. In addition, the vectoring engine can keep a record of        the responsibilities and resources available to each node and        their state—relative to the greater activity and portion        assigned to the node, including providing updated reports to a        monitoring agent.    -   R. Mobile apps are not designed to echo a specific object and,        like a baton, pass from one user to another to signify the        transfer and possession of the object. Vectoring engines can        echo a specific object and, like a baton, pass from one user to        another to signify the transfer and possession of the object. In        addition, the vectoring engine can keep a record of the        transfers and possessors, including providing updated reports to        a monitoring agent.    -   S. The performance of mobile apps is not directly driven by        videogame-like nonlinear storyboards; which allow for deviations        from the norm. The performance of a vectoring engine is driven        by videogame-like nonlinear storyboard; which allows for        deviations from the norm. In addition, sensitive to “subsequent”        transmissions a vectoring engine can operate without a graphic        user interface to trigger automated responses by its        (algorithmic) service modules.    -   T. A collection of mobile apps cannot be searched for the        keywords and dates they contain. A collection of vectoring        engines can be searched for the keywords and dates they contain.    -   U. Mobile apps cannot be made responsive to a personal calendar        or a group calendar or operate inside a unified messaging schema        and app management environment. Vectoring engines are responsive        to personal and group calendars and designed to operate inside a        unified messaging schema and app management environment.    -   V. Mobile apps are not designed to operate in parent/child        dependency relationship. Vectoring engines are designed to        operate in parent/child dependency relationships.    -   W. Mobile apps are not designed to create a secure information        space. Vectoring engines by their very nature create a secure        information and communications space between the parties that is        unique to each instance of a vectoring engine. In addition, the        system utilizes an “alternate path” response methodology.    -   X. Mobile apps are not designed to create situation-sensitive        communication and information sharing networks between the        parties (including machines).    -   Y. Mobile apps are not designed to be “framed” by other software        applications that tap their workings to perform sympathetic        functions; some of which may add another layer of functionality        to the mobile app and/or create another mobile app that uses the        output of the “frame” to perform a function that's sympathetic        to the frame that its linked to and is also capable of being        “framed” by another software application. Vectoring engines,        singularly or in groups, are designed to be “framed” by other        software applications that tap their workings to perform        sympathetic functions; some of which may add another layer of        functionality to the vectoring engine(s) and/or create another        vectoring engine that uses the output of the “frame” to perform        a function that's sympathetic to the frame that its linked to        and is also capable of being “framed” by another software        application.    -   Z. Mobile apps are not designed to be driven by library-based        numerical codes, stamps, and indexes. Vectoring engines are        designed to be driven by library-based numerical stamps, codes,        and indexes.

The vectoring engines of the disclosure may be differentiated from theWeb in the following non-limiting ways: (In broad terms, the Web is aninformation sharing system and the disclosure is directed to an activitysupport system.)

-   -   A. The core information supporting instrument of the Web is a        website consisting of one or more pages. The activity supporting        instrument in the system is a resource vectoring engine.    -   B. The Web is a hypertext web-like environment, the system is a        mission-oriented hub and spoke computing environment.    -   C. The Web relies on the use of a browser. The system does not        rely on a browser.    -   D. While Coordinated Universal Time (UTC) has some relevance to        the Web, it is inseparable from almost every operation within        the system.    -   E. The Web is a passive system that relies heavily on the        Internet's Hypertext Transfer Protocol. The system is a        proactive system that relies on distributed computing and        metadata, and event signaling.    -   F. The Web is not reliant on mobile devices. Mobile devices are        integral to the operation of the system.    -   G. Search engines are integral to the Web. Web-style search        engines are not part of the systems schema, although may be        incorporated therein.    -   H. The Web is not designed to protect its users' identity and        the sanctity of their communications. The system is designed to        protect its users' identity (privacy) and the sanctity of their        communications. In addition, the system utilizes an “alternate        path” response methodology.    -   I. The Web does not include a uniform monetization platform. The        system includes an optional a transactional, uniform        monetization platform.    -   J. The Web does not include a uniform financial clearing port        necessary to provide comprehensive support for the buying and        selling of goods and services. The system includes a uniform        financial clearing port to provide comprehensive support for the        buying and selling of goods and services.    -   K. The Web does not know why someone is using it. The system        knows precisely why an individual is using it.    -   L. The Web does not require or support user registration. The        system allows user registration, but does not require that its        users disclose their identity.    -   M. The Web has a “one-size-fits-all” architecture. The system        supports intermediary platforms that customize the architecture        within categories of usage. In addition, it can support        regulated communications between the intermediary platforms.

Accordingly, the present disclosure provides various systems, servers,methods, media, and programs. Although the disclosure has been describedwith reference to several exemplary embodiments, it is understood thatthe words that have been used are words of description and illustration,rather than words of limitation. Changes may be made within the purviewof the appended claims, as presently stated and as amended, withoutdeparting from the scope and spirit of the disclosure in its aspects.Although the disclosure has been described with reference to particularmeans, materials and embodiments, the disclosure is not intended to belimited to the particulars disclosed; rather the disclosure extends toall functionally equivalent structures, methods, and uses such as arewithin the scope of the appended claims.

While the computer-readable medium may be described as a single medium,the term “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the embodiments disclosed herein.

The computer-readable medium may comprise a non-transitorycomputer-readable medium or media and/or comprise a transitorycomputer-readable medium or media. In a particular non-limiting,exemplary embodiment, the computer-readable medium can include asolid-state memory such as a memory card or other package that housesone or more non-volatile read-only memories. Further, thecomputer-readable medium can be a random access memory or other volatilere-writable memory. Additionally, the computer-readable medium caninclude a magneto-optical or optical medium, such as a disk or tapes orother storage device to capture carrier wave signals such as a signalcommunicated over a transmission medium. Accordingly, the disclosure isconsidered to include any computer-readable medium or other equivalentsand successor media, in which data or instructions may be stored.

Although the present application describes specific embodiments whichmay be implemented as code segments in computer-readable media, it is tobe understood that dedicated hardware implementations, such asapplication specific integrated circuits, programmable logic arrays andother hardware devices, can be constructed to implement one or more ofthe embodiments described herein. Applications that may include thevarious embodiments set forth herein may broadly include a variety ofelectronic and computer systems. Accordingly, the present applicationmay encompass software, firmware, and hardware implementations, orcombinations thereof.

Although the present specification describes components and functionsthat may be implemented in particular embodiments with reference toparticular standards and protocols, the disclosure is not limited tosuch standards and protocols. Such standards are periodically supersededby faster or more efficient equivalents having essentially the samefunctions. Accordingly, replacement standards and protocols having thesame or similar functions are considered equivalents thereof.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the various embodiments. Theillustrations are not intended to serve as a complete description of allof the elements and features of apparatus and systems that utilize thestructures or methods described herein. Many other embodiments may beapparent to those of skill in the art upon reviewing the disclosure.Other embodiments may be utilized and derived from the disclosure, suchthat structural and logical substitutions and changes may be madewithout departing from the scope of the disclosure. Additionally, theillustrations are merely representational and may not be drawn to scale.Certain proportions within the illustrations may be exaggerated, whileother proportions may be minimized. Accordingly, the disclosure and thefigures are to be regarded as illustrative rather than restrictive.

One or more embodiments of the disclosure may be referred to herein,individually and/or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any particular invention or inventive concept. Moreover,although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b) and is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, various features may begrouped together or described in a single embodiment for the purpose ofstreamlining the disclosure. This disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may be directed toless than all of the features of any of the disclosed embodiments. Thus,the following claims are incorporated into the Detailed Description,with each claim standing on its own as defining separately claimedsubject matter.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present disclosure. Thus, to the maximumextent allowed by law, the scope of the present disclosure is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A computer-implemented method of managingcomputer network resources by one or more processors, the methodcomprising: receiving data acquired from an external device over acommunication network; storing operational programs and related data ina computer-readable storage medium; compiling, by the one or moreprocessors, the data acquired from the external device into a liveobject; linking, by the one or more processors, resources identified inthe live object via service modules and interfaces; activating the linksof the identified resources to acquire information from the resourcesand to personalize performance of the resources; creating, by the one ormore processors, a vectoring engine to implement specific objectives ofthe live object and an active plate, and a box that establishes anindependent relationship with the live object; managing, by the one ormore processors, the service modules and interfaces of the system toexecute the specific objectives, and the box to query data contained inthe live object; and transmitting results of the executed specificobjectives over the network to the external device.
 2. Thecomputer-implemented method according to claim 1, further comprising: aplurality of live objects, wherein the box queries and interacts withdata contained in one or more of the plurality of live objects.
 3. Thecomputer-implemented method according to claim 2, further comprising: aplurality of boxes, wherein one or more of the plurality of boxes queryand interact with the data contained in the one or more of the pluralityof live objects.
 4. The computer-implemented method according to claim3, wherein a primal object is used by a first box of the plurality ofboxes to service as a primal object that serves as a genericrepresentation of a subject of a query of the data contained in the oneor more of the plurality of live objects.
 5. The computer-implementedmethod according to claim 1, wherein the box include one or more otherboxes, with each superior box in a hierarchy of the one or more otherboxes defining its own relationships and outputs.
 6. Thecomputer-implemented method according to claim 1, wherein the one ormore processors include a socket interface that permits interaction withexternal support services.
 7. The computer-implemented method accordingto claim 6, wherein the external support services provide supportservices to a user virtualization framework component.
 8. Thecomputer-implemented method according to claim 6, wherein the externalsupport services provide support services to a vectoring enginemanager/player framework component.
 9. The computer-implemented methodaccording to claim 6, wherein the external support services providesupport services to one or more specialized service components.
 10. Thecomputer-implemented method according to claim 1, wherein the one ormore processors include a socket interface that permits the addition ofan interactive deep learning component.
 11. The computer-implementedmethod according to claim 1, wherein the interactive deep learningcomponent interacts with one or more specialized service components. 12.A system for managing computer network resources, comprising: one ormore processors; a computer-readable storage medium that storesoperational programs and related data; a receiver that receives dataacquired from an external device over a communication network; and atransmitter to transmit data processed by the one or more processorsover the communication network to the external device the one or moreprocessors, wherein the one or more processors compile the data acquiredfrom the external device into a live object; link resources identifiedin the live object via service modules and interfaces; activate thelinks of the identified resources to acquire information from theidentified resources and personalize performance of the resources;create a vectoring engine to implement specific objectives of the liveobject and an active plate, create a box that establishes an independentrelationship with the live object; manage the service modules andinterfaces of the system to execute the specific objectives, manage thebox to query data contained in the live object, and enable thetransmitter to transmit results of the executed specific objectives overthe network to the external device.
 13. The system according to claim12, wherein the one or more processors compile the data acquired fromthe external device into a plurality of live objects.
 14. The systemaccording to claim 13, wherein the box queries and interacts with datacontained in one or more of the plurality of live objects.
 15. Thesystem according to claim 13, wherein the one or more processors createa plurality of boxes that establish independent relationships with oneor more of the plurality of live objects.
 16. The system according toclaim 15, wherein one or more of the plurality of boxes query andinteract with the data contained in the one or more of the plurality oflive objects.
 17. The system according to claim 15, wherein a primalobject is used by a first box of the plurality of boxes to service as aprimal object that serves as a generic representation of a subject of aquery of the data contained in the one or more of the plurality of liveobjects.
 18. The system according to claim 12, wherein the box includeone or more other boxes, with each superior box in a hierarchy of theone or more other boxes defining its own relationships and outputs. 19.A computer-readable storage device that stores a set of instructions formanaging computer network resources, the instructions, when executed,causing one or more processors to perform operations, comprising:receiving data acquired from an external device over a communicationnetwork; storing operational programs and related data in acomputer-readable storage medium; compiling the data acquired from theexternal device into a live object; linking, resources identified in thelive object via service modules and interfaces; activating the links ofthe identified resources to acquire information from the resources andto personalize performance of the resources; creating a vectoring engineto implement specific objectives of the live object and an active plate,and creating a box that establishes an independent relationship with thelive object; managing the service modules and interfaces to execute thespecific objectives, and managing the box to query data contained in thelive object; and transmitting results of the executed specificobjectives over the communication network to the external device. 20.The computer-readable storage device according to claim 19, theoperations further comprising: compiling the data acquired from theexternal device into a plurality of live objects; and creating aplurality of boxes, wherein one or more of the plurality of boxes queryand interact with data contained in the one or more of the plurality oflive objects.